Feature: Add campaign categories filter sidebar (#602) - #750

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow files =="
git ls-files '.github/workflows/*' || true

echo "== target workflow excerpt =="
if [ -f .github/workflows/deploy-storybook.yml ]; then
  cat -n .github/workflows/deploy-storybook.yml
else
  echo "target workflow not found"
fi

echo "== search for storybook-static usage and defaults/working-directory =="
rg -n "storybook-static|defaults:\s*run:\s*working-directory|working-directory:|uses: peaceiris/actions-gh-pages|build-storybook|storybook" -S .

echo "== git status/stat =="
git status --short || true
git diff --stat || true

Repository: ritik4ever/stellar-goal-vault

Length of output: 3787

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== frontend package scripts and config files =="
cat -n frontend/package.json

echo "== storybook config files =="
git ls-files frontend | rg '(^|/)(.storybook|storybook\.config|vite\.config|package\.json)$' || true

for f in frontend/.storybook/main.ts frontend/.storybook/main.js frontend/.storybook/main.cjs frontend/.storybook/main.mjs frontend/.storybook/preview.ts frontend/.storybook/preview.js frontend/.storybook/preview.cjs frontend/.storybook/preview.mjs frontend/vite.config.ts frontend/vite.config.js frontend/package.json; do
  if [ -f "$f" ]; then
    echo "--- $f"
    cat -n "$f"
  fi
done

echo "== action usage refs =="
rg -n "peaceiris/actions-gh-pages" .github/workflows packages.json package.json 2>/dev/null || true

Repository: ritik4ever/stellar-goal-vault

Length of output: 5773

🌐 Web query:

GitHub Actions workflow syntax defaults.run.working-directory apply only to run steps

💡 Result:

Yes, the GitHub Actions workflow syntax for defaults.run.working-directory applies exclusively to run steps [1][2][3]. According to official GitHub documentation, the defaults.run keyword is used to provide default shell and working-directory options specifically for all run steps within a workflow or a job [1][4][5]. This setting does not affect other types of steps, such as those that use uses to invoke actions [6]. Actions executed via uses manage their own execution environment and are not impacted by the defaults.run configuration [6]. To summarize the scope: - It applies to run steps (commands executed directly in the shell) [1][2]. - It does not apply to steps that utilize uses (actions) [6]. - You can set these defaults at the workflow level (under defaults:) or override them at the job level (under jobs.<job_id>.defaults:) [1][2][3]. Job-level settings take precedence over workflow-level settings [1][3].

Citations:

• 1: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax?use_case=
• 2: https://docs.github.com/en/enterprise-cloud@latest/actions/how-tos/write-workflows/choose-what-workflows-do/set-default-values-for-jobs
• 3: https://docs.github.com/en/enterprise-cloud@latest/actions/reference/workflows-and-actions/workflow-syntax
• 4: https://docs.github.com/en/enterprise-server@3.20/actions/how-tos/write-workflows/choose-what-workflows-do/set-default-values-for-jobs
• 5: https://docs.github.com/en/enterprise-server@3.21/actions/reference/workflows-and-actions/workflow-syntax
• 6: @actions/exec seems to ignore working-directory workflow setting actions/toolkit#841

🌐 Web query:

peaceiris actions-gh-pages v3 publish_dir working directory behavior

💡 Result:

In peaceiris/actions-gh-pages (including v3), the publish_dir option specifies the source directory within your repository that contains the static files you wish to deploy to the gh-pages branch [1][2]. The contents of this specified directory are copied to the root of the target branch (gh-pages by default) [1][3]. Key behaviors regarding publish_dir include: 1. Default Directory: If not specified, the action defaults to using a directory named public in the root of your repository [1][3]. 2. Path Resolution: The path provided to publish_dir is relative to the workspace root (GITHUB_WORKSPACE) [4][5]. 3. Repository Root Interaction: If you set publish_dir to. (the repository root), the action may inadvertently attempt to delete or modify the.git directory within the workspace, which can cause deployment failures [4]. It is generally recommended to use a dedicated subdirectory (e.g.,./dist or./public) for your build artifacts to avoid this [6]. 4. Cleanup Behavior: By default, the action removes existing files in the target branch before deploying the new contents from publish_dir [7]. You can use the keep_files option if you wish to preserve existing files in the target branch [8][7]. For complex setups where you need to deploy specific files or handle directories already present in the workspace, common practices include creating a dedicated build output directory or using a post-build step to copy all necessary assets into a single directory before calling the action [6][5].

Citations:

• 1: https://github.com/peaceiris/actions-gh-pages/blob/main/README.md
• 2: https://github.com/peaceiris/actions-gh-pages/tree/v3.8.0
• 3: https://github.com/peaceiris/actions-gh-pages
• 4: Not delete .git directory when publish_dir is GITHUB_WORKSPACE peaceiris/actions-gh-pages#548
• 5: Publish Jekyll locally generated main branch _site subdir to gh-pages branch for GitHub Pages User site? peaceiris/actions-gh-pages#596
• 6: How to add dist/ directory? peaceiris/actions-gh-pages#570
• 7: https://github.com/peaceiris/actions-gh-pages/releases/tag/v2.4.0
• 8: New Option destination_dir for deploying to a subdirectory peaceiris/actions-gh-pages#324

🌐 Web query:

peaceiris actions-gh-pages v4 README publish_dir

💡 Result:

In the peaceiris/actions-gh-pages version 4 GitHub Action, the publish_dir input specifies the source directory containing the static files you wish to deploy to GitHub Pages [1][2]. Key details regarding publish_dir include: - Function: It defines the directory from which the action will copy and deploy files [1][3]. - Default Value: The default directory is./public [1][2][4]. - Behavior: Only the contents of the specified directory are pushed to the target branch (which defaults to gh-pages) [1][3]. Example usage in a workflow file: - name: Deploy uses: peaceiris/actions-gh-pages@v4 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir:./public

Citations:

• 1: https://github.com/peaceiris/actions-gh-pages?tab=readme-ov-file
• 2: https://github.com/peaceiris/actions-gh-pages/blob/main/README.md
• 3: https://github.com/marketplace/actions/github-pages-action
• 4: https://github.com/peaceiris/actions-gh-pages

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/sh
rg -n -P '^import\s+type\s+\{[^}]*\buseState\b' frontend/src/components/PledgeForm.tsx
rg -n '\buseState\s*\(' frontend/src/components/PledgeForm.tsx

Repository: ritik4ever/stellar-goal-vault

Length of output: 313

🏁 Script executed:

#!/bin/sh
set -eu

printf '--- PledgeForm relevant section ---\n'
sed -n '1,120p' frontend/src/components/PledgeForm.tsx

printf '\n--- TypeScript config flags affecting import-namespace/type-only behavior ---\n'
find . -maxdepth 3 -path './frontend/**' -o -path './node_modules/**' -prune 2>/dev/null | grep -E '(^|/)(tsconfig.*\.json|package\.json)$' | while read -r f; do
  if [ -f "$f" ]; then
    sed -n '1,220p' "$f" | grep -n -E '"importsNotUsedAsValues"|"verbatimModuleSyntax"|"isolatedModules"|"noUnusedLocals"|"type":"module"|typeOnly|tsx|jsx' || true
  fi
done

printf '\n--- React imports in nearby files ---\n'
rg -n "^import (?:type )?\\{[^\\n]*useState\\}" frontend/src -g '*.tsx' -g '*.ts' | head -50

Repository: ritik4ever/stellar-goal-vault

Length of output: 258

🏁 Script executed:

#!/bin/sh
set -eu

printf '%s\n' '--- PledgeForm relevant section ---'
sed -n '1,120p' frontend/src/components/PledgeForm.tsx

printf '%s\n' ''
printf '%s\n' '--- TypeScript config flags affecting import behavior ---'
find . -maxdepth 3 \( -path './node_modules/*' -prune \) -o \( -type f \( -name 'tsconfig*.json' -o -name 'package.json' \) \) -print | sort | while read -r f; do
  if [ -f "$f" ]; then
    printf '%s\n' "--- $f ---"
    sed -n '1,220p' "$f" | grep -n -Ei '"importsNotUsedAsValues"|"verbatimModuleSyntax"|"isolatedModules"|"noUnusedLocals"|"type":"module"|importsNotUsedAsValues|verbatimModuleSyntax|isolatedModules|noUnusedLocals|typeOnly|tsx|jsx' || true
  fi
done

printf '%s\n' ''
printf '%s\n' '--- useState import usage in frontend source ---'
rg -n "^import (?:type )?\\{[^\\n]*useState\\}" frontend/src -g '*.tsx' -g '*.ts' | head -80 || true

printf '%s\n' ''
printf '%s\n' '--- runtime-state check if tsconfig exists ---'
if [ -f frontend/tsconfig.json ]; then cat frontend/tsconfig.json; fi
if [ -f tsconfig.json ]; then cat tsconfig.json; fi

Repository: ritik4ever/stellar-goal-vault

Length of output: 5170

🌐 Web query:

TypeScript import type erases type imports used at runtime error TS2455

💡 Result:

The error TS2455, as described in your query, relates to the fundamental behavior of the import type syntax in TypeScript. It is important to clarify that import type is a compile-time-only construct guaranteed to be fully erased from the emitted JavaScript [1][2]. If you are encountering an error related to import type being "erased at runtime," it is likely because you are attempting to use an imported type as a value in your code [3][4]. Because import type declarations are completely removed during transpilation, the imported identifier does not exist in the generated JavaScript code [1][3]. Consequently, using it as a value (e.g., new MyType() or console.log(MyType)) is invalid and will trigger a TypeScript error [3][4]. To resolve this issue: 1. Check for Value Usage: Ensure that any identifier imported via import type is used only in type positions (e.g., in type annotations, implements clauses, or generic arguments) [1][2]. 2. Switch to Regular Imports: If you need to use the imported identifier as a value at runtime, you must use a standard import statement (e.g., import { MyValue } from './module') instead of import type [3][4]. 3. Module System Considerations: Note that using import or import type statements at the top level of a file will cause TypeScript to treat the file as a module [5][6]. If you are in a non-module environment or trying to mix ES modules and CommonJS, this can sometimes lead to module resolution errors [5][7]. In some specific cases where you need to reference a type without triggering module-level side effects or resolution issues, you can use the inline import() syntax: type MyType = import('./module').MyType; [5][6] If you believe you are seeing TS2455 specifically in a context that does not match this, please double-check the exact error message, as TS2455 is not a standard, commonly cited code for "import type erasure"; standard behavior for type-only imports is to simply be removed without error unless they are misused as values [3][2]. If the error persists, it may be a misconfiguration of your module resolution settings or a confusion with other module-related errors [5][7].

Citations:

• 1: https://www.typescriptlang.org/docs/handbook/modules/reference.html
• 2: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html
• 3: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/website/blog/2023-02-24-consistent-type-exports-and-imports-why-and-how.md
• 4: https://www.typescriptlang.org/docs/handbook/modules/reference
• 5: import type should not need runtime modules support microsoft/TypeScript#44549
• 6: import type should not have any effect on output code microsoft/TypeScript#41562
• 7: https://exchangetuts.com/why-wont-typescript-let-me-import-a-type-from-an-es-module-into-a-commonjs-module-1768566602943785

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

schema="$(mktemp)"
trap 'rm -f "$schema"' EXIT

curl -fsSL \
  'https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json' \
  > "$schema"

jq -e '.properties["breaking-change-keywords"]' "$schema" >/dev/null

Repository: ritik4ever/stellar-goal-vault

Length of output: 167

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

printf '--- release-please-config.json relevant lines ---\n'
cat -n release-please-config.json | sed -n '1,80p'

printf '\n--- release workflow action pins ---\n'
if [ -f .github/workflows/release.yml ]; then
  cat -n .github/workflows/release.yml | sed -n '1,220p'
else
  echo ".github/workflows/release.yml not found"
fi

printf '\n--- search for schema/config references ---\n'
rg -n '"breaking-change-keywords"|release-please|config-file|schema|additionalProperties|properties' .github release-please-config.json 2>/dev/null || true

Repository: ritik4ever/stellar-goal-vault

Length of output: 258

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

printf '%s\n' '--- release-please-config.json relevant lines ---'
cat -n release-please-config.json | sed -n '1,80p'

printf '%s\n' ''
printf '%s\n' '--- release workflow action pins ---'
if [ -f .github/workflows/release.yml ]; then
  cat -n .github/workflows/release.yml | sed -n '1,220p'
else
  echo ".github/workflows/release.yml not found"
fi

printf '%s\n' ''
printf '%s\n' '--- search for schema/config references ---'
rg -n '"breaking-change-keywords"|release-please|config-file|schema|additionalProperties|properties' .github release-please-config.json 2>/dev/null || true

printf '%s\n' ''
printf '%s\n' '--- all tracked release-please config files ---'
git ls-files '*release-please-config.json' '*release-please*' config.json 2>/dev/null || true

Repository: ritik4ever/stellar-goal-vault

Length of output: 5744

🌐 Web query:

google-github-actions release-please-action v4 breaking-change-keywords config-file schemas config.json

💡 Result:

The release-please-action v4 requires the use of a manifest-based configuration rather than many of the legacy action inputs [1][2]. Regarding "breaking-change-keywords," release-please follows the Conventional Commits specification by default [3][4]. According to this standard, breaking changes are indicated by appending an exclamation mark (!) to the type/scope (e.g., feat!: or fix!:) or by using a footer with "BREAKING CHANGE:" [5]. There is no explicit "breaking-change-keywords" configuration option in the current release-please-config.json schema [6]. Instead, the tool automatically detects breaking changes based on these standard Conventional Commit patterns [5]. Key details regarding v4 and configuration: 1. Migration to googleapis: Development has moved from google-github-actions/release-please-action to googleapis/release-please-action [5][7]. Users should update their workflows to use the new repository [5][3]. 2. Config File Schema: The official configuration is defined in release-please-config.json [6]. The schema for this file is maintained by the upstream release-please project [6]. You can validate your configuration against the official schema located at https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json [6][8]. 3. Configuration Format: In v4, most configuration is handled via a release-please-config.json file in your repository [3][9]. The action input config-file allows you to specify the path to this file (defaulting to release-please-config.json) [3][10]. 4. Inline Overrides: If you prefer not to use a separate configuration file for simple setups, you can use the config-overrides-json input to provide configuration options as a JSON string directly within your workflow file [9]. For advanced configuration, such as setting custom changelog sections or release types, refer to the official manifest-releaser documentation [3][11].

Citations:

• 1: https://github.com/googleapis/release-please-action/releases/tag/v4.0.0
• 2: https://github.com/googleapis/release-please-action/blob/main/CHANGELOG.md
• 3: https://github.com/googleapis/release-please-action
• 4: https://github.com/googleapis/release-please/blob/main/docs/customizing.md
• 5: https://pkg.go.dev/github.com/google-github-actions/release-please-action@v4.1.1+incompatible
• 6: https://catalog.lintel.tools/schemas/schemastore/release-please-config-json/
• 7: google-github-actions/release-please-action@google-github-actions:a37ac6e...google-github-actions:e4dc86b
• 8: https://github.com/google/dotprompt/blob/0911cf9e/.github/workflows/validate-release-please-config.yml
• 9: https://github.com/release-please-oss/release-please-action
• 10: https://github.com/marketplace/actions/release-please-action
• 11: https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

schema="$(mktemp)"
trap 'rm -f "$schema"' EXIT

curl -fsSL \
  'https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json' \
  > "$schema"

printf '%s\n' '--- top-level breaking-change-keywords property ---'
jq '.properties["breaking-change-keywords"]' "$schema"

printf '%s\n' ''
printf '%s\n' '--- property names containing breaking-change or changelog ---'
jq -r '.properties | to_entries[] | select(.key|test("break|change|changelog|packages|changelog-path"; "i")) | .key' "$schema"

printf '%s\n' ''
printf '%s\n' '--- package-level properties containing changelog/breaking/change ---'
jq -r '.properties.packages.type.description // empty, .properties.packages.properties | to_entries[] | select(.key|test("break|change|changelog|package-name"; "i")) | .key' "$schema"

printf '%s\n' ''
printf '%s\n' '--- schema additionalProperties settings ---'
jq -r '{top: .additionalProperties, packages: .properties.packages.properties."additionalProperties"}' "$schema"

Repository: ritik4ever/stellar-goal-vault

Length of output: 527